Add Cloud SQL Auth Proxy IAM authentication#66510
Merged
shahar1 merged 4 commits intoMay 12, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds support for Cloud SQL Auth Proxy IAM DB authentication in the Google Cloud SQL integration by introducing a new sql_proxy_enable_iam_login option that maps to the proxy’s -enable_iam_login flag, allowing connections with an empty password when using the proxy.
Changes:
- Add
sql_proxy_enable_iam_loginplumbing toCloudSqlProxyRunnerandCloudSQLDatabaseHook, including validation and connection-URI/parameters handling for empty passwords. - Add unit tests covering Postgres/MySQL proxy IAM behavior and flag propagation to the proxy runner.
- Add a new system test example DAG and update connection documentation to describe the two IAM authentication paths.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
providers/google/src/airflow/providers/google/cloud/hooks/cloud_sql.py |
Adds the new sql_proxy_enable_iam_login parameter, validation, and proxy flag injection. |
providers/google/tests/unit/google/cloud/hooks/test_cloud_sql.py |
Adds unit tests for proxy IAM behavior, empty-password URI generation, and proxy runner flag behavior. |
providers/google/tests/system/google/cloud/cloud_sql/example_cloud_sql_query_proxy_iam.py |
Adds a system test example DAG demonstrating proxy IAM authentication flow. |
providers/google/docs/connections/gcp_sql.rst |
Documents direct IAM token auth vs proxy IAM auth and updates password requirements accordingly. |
…dation and clarity
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes: #35347
How
Add the
sql_proxy_enable_iam_loginparameter to support-enable_iam_logininCloudSqlProxyRunner.What
Reproducer DAG:
Connection:
{ "conn_type": "gcpcloudsql", "login": "<your-sa-name>@<your-project>.iam.gserviceaccount.com", "password": "", "host": "127.0.0.1", "port": 5432, "schema": "test_db", "extra": { "database_type": "postgres", "project_id": "<your-project>", "location": "us-central1", "instance": "<your-instance-name>", "use_proxy": "True", "sql_proxy_use_tcp": "True", "sql_proxy_enable_iam_login": "True" } }Before fix
After fix
System test
Cloud SQL instance lifecycle (create → delete) executed as expected.

Was generative AI tooling used to co-author this PR?
Generated-by: Codex 5.5 following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.